Should we ping the maintainers first?

Sure, @SimenB @broofa

👋

The linked gist with logs in #1060 (comment) has no data - did it timeout? If yes, can we increase the timeout? If we cannot increase the timeout I'd like for us to skip some tests rather than removing Jest entirely (e.g. watch and transform tests take almost a minute, even on my m2 max)

I'm unable to view the mime test report linked at the bottom of #1060 (comment). (I get this same error for everything on Jenkins, though... so maybe an issue with my account permissions?)

It was not a timeout and yeah, I think you won't be able to see the Jenkins UI since we are in lockdown due to the security release.

I can re-run it after the security release, but both modules were failing due to "MODULE_NOT_FOUND". Jest: https://gist.github.com/RafaelGSS/57c21139d9f27e855217d5f1e59ff511.

FWIW, that gist appears to be specific to jest. It refers to the isolated-vm module, which isn't a part of mime's source or dependencies.

So... I guess ping me when the lockdown is lifted? (Sorry, I'm not familiar enough with the CITGM project to know how lockdowns work or how long they last.)

@broofa Here's how mime fails : https://gist.github.com/targos/d3fb84c45a67a4bd26ee7de25d66652b

Okay, I've pushed mime@4.0.4 which should fix this issue. (npm test script wasn't compiling TS files)

Hit me up if the problem doesn't go away.

Thanks! CI for mime: https://github.com/nodejs/citgm/actions/runs/9818510101

@RafaelGSS mime is passing again (we already skip it on win32)

The Jest one is a red herring - it's just a logged error not an actual failure. https://github.com/jestjs/jest/blob/9c9ce8ad80c6719c3378dd0058c173830621a3ff/e2e/__tests__/nativeEsm.test.ts#L31

I can probably avoid logging it, tho.

EDIT: jestjs/jest#15166

Thank you folks!